Add property to prevent scanning all @Value annotation by default. #103
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Desired Outcome
The goal of this PR is to prevent default scanning of all
@Value
annotations by defaultThis can have huge performance impact on application startup: In real customer context, application slowed from 21s to 170s as of too many invalid secrets retrieval.
With the following code:
Developer will get as result:
Implemented Changes
This PR introduces new property
conjur.scan-all-values
that allow the developer to explicitly enable all@Value
annotation scanning.The bean
ConjurCloudProcessor
will be loaded only ifconjur.scan-all-values
is set to true andConjurPropertySource
bean is not present.Definition of Done
At least 1 todo must be completed in the sections below for the PR to be
merged.
Changelog
CHANGELOG update
Test coverage
changes, or
Documentation
README
s) were updated in this PRBehavior
Security